Cream of the Crop 25

home *** CD-ROM | disk | FTP | other *** search

/ Cream of the Crop 25 / Cream of the Crop 25.iso / bbs / outil179.zip / OEVENT.DOC < prev next >

Wrap

Text File | 1997-04-30 | 16KB | 436 lines

OPUS <TM> EVENT muncher Version 8.00 June 20, 1990 One of the things about the continued growth of OPUS is that it con- stantly needs new utilities to maintain it. Hopefully this program will fill one of the needs for the people who are using OPUS 1.10 with its extended scheduling commands. OEVENT should be fairly simple to use, just type in: OEVENT [FILENAME.EXT] [/C] [/L [> PRN:] [>FILE.EXT] ] If no file is specified OEVENT will look for SCHED.DAT. The '/C' option will Create a new schedule file for OPUS with one ex- ternal event at midnight, for one minute, and keep the schedule in memory for editing. You do need one external event with OPUS each day. Just "OEVENT /C" will create SCHED.DAT, ready to edit. The '/L' option will List the events in the file specified, or if no file is specified, in SCHED.DAT. The screen will look like this: ------------------------------------------------------------------ Event Tag Day Start End Run? Exit Mail LO CM SX MO FR Caller Count = 982 Quote Position = 9800 <5> <6> <7> <8> <9> <0> 0 Z SMTWTFS 0:00 0:55 DIS Y N Y N N Y 0 1 Z SMTWTFS 0:55 2:00 ENA Y N N N Y N 0 2 * X SMtWtFs 0:57 0:57 ENA F 31 3 X smTwTfS 0:57 0:57 ENA F 30 4 * X SMTWTFS 2:00 2:01 ENA I 50 5 Z SMTWTFS 2:00 6:45 ENA Y N Y N N Y 5 6 * X SMTWTFS 4:30 4:30 ENA I 60 7 Z Smtwtfs 6:45 17:00 ENA Y N Y N N Y 0 8 Z smtwtfS 6:45 10:00 ENA Y N Y N N Y 0 <-> Previous Event <+> Next Event <N> Jump to N <O> Sort <S> Start Time <E> End Time <M> Move Event <D> Day-of-week <*> Edit Everything <Z> Edit Behavior <T> Event Tag <R> Error Level <F> Forced Event <I> Informal <G> Use GMT <Y> Use Hybrid <1> Dis/Enable Event <2> Insert Event <3> Delete Event <C> Cost of Local <P> Delay Factor <L> Flush to disk <Q> Quit <ESC> Abort By your command? The Commands: --- --------- Most commands can be reached two or three ways. This is primarily to make sure that OEVENT will run on anything that OPUS will run on, but also means that you can pick any command set that you are comfortable with. "-", "_", Move Up Move to lower-number event, up on the scr- een. (Up Arrow on IBM and compatibles will also work) "+", "=" Move Down Move to higher-number event, down on the screen. (Down Arrow will also work on IBM and close compatibles) "<", ",", PgUp Page Up Moves up 8 Events, one screen full. ">", ".", PgDn Page Down Move down 8 Events, one screen full. H, Home Move to Event #0. End Jump to last event. ")" Quote Position Sets the QuotePosition to 0. "!" CallerCount Alter the CallerCount. Q Quit, Save the changes and exit. ESC Abort Abort this run. Do NOT save any of the changes. L Flush Saves the current schedule file to disk but continue the edit. S Start Time Set the time that this event will start in Hour:Min, 24-hour format. E End Time Set the End of this event in Hour:Minute format. M Move Time Move the start and end times of this even- t. (Opus doesn't look at the "length" of an event, only the start and end times) F Forced Event Make this a Forced Event. OPUS will run this event as soon as possible if someth- ing creates a situation where the event is missed. (i.e. A user does a big upload just before the event, mail packet is bei- ng transferred, etc.) I Informal Mark this as an Informal Event. Opus will run this as soon as it is free after the start time for this event. R Error Level Set the Error Level for External Events or the length of time the bell will ring for Y)ell event. In a Behavior Event, sets the error offset, the amount that will be added to an errorlevel when Opus exits. D Day-of-Week Set the Day of Week that this event runs. (0=Sunday, 1=Monday, ... 7=All, 8=Weekd- ays, 9=Weekend) Events are now TOTALLY bit-masked so you can have ANY combinatio- n, such as MWF. In the display the Days-of-Week when the event is ON will be in uppercase, the days when the event will not run are lower c- ase. V Event done Marks this event as done for today. In the display there will be an asterisk between the event number and its tag. The 'V' key will toggle this off and on. T Event Tag Change the Event Tag. H Housekeeping, clears all the *.$$? files from Outbound directory. S ScanAll Run the OPUS internal EchoMail scanner. X External Event, Errorlevel set by R com- mand above. Y Yell Event. When do you want users to be able to get your attention. Z Behavior Event. Controls the way OPUS will handle mail, do Scans, and take care of the Outbound directory. U USER Event. Modifies the time/download limitation for users during this event. M Use external mailer instead of Opus inter- nal mail. Opus will load itself, and then it will load the mailer as listed in your PRM file. Since Opus is already in memory and initialized, it won't affect users very much. But it is going to take a lot of memory for this. I Use Opus internal mail. Basically, if the PRM file has been set to use an external mailer, this overrides it. O Sort Events Sorts events by Start Time. Should help you keep straight what is going on. * Edit Everything Go through all the commands for an event, automatically sets Event as Enabled. Z Edit Behavior Modify the way OPUS will handle outbound mail. Will give you a new Menu with spe- cific commands. You can also alter the way OPUS will handle outbound mail dur- ing this event from the main menu, shown above, by using the numeric (or Function Keys on IBM compatibles) as listed here: 4 Toggle Send Mail during this event. 5 Toggle Local Mail Only, for those boards that are below the current "local" cost definition. 6 Toggle No-Local mail. Opus below "local" cost definition will not be sent. 7 Toggle Continuous-Mail only. Send only mail marked as "Crash" to another board that can accept mail 24 hours. 8 Toggle Suppress Exits. If Yes, OPUS will NOT Exit when Crash-Mail or other reasons control- led by CTL file. 9 Toggle Mail-Only. If Yes, will not accept human callers. 0 Toggle File-Requests. If Yes, File-Requests will be honored. If No, will refuse them. C Cost What Opus should consider to be a "local" call if local-only is set to on during this Behavior Window. Calls that have a cost less than or equal to this value in your nodelist will be placed during this Behavior Window. P Frequency Adjusts how often Opus will make outgoing calls. Can be any value between 5 and 40, with a Frequency=15 being roughly 1.5 minutes between calls, a value of 5 being about 10 seconds apart, a value of 40 will give you a longer delay between calls, about 10 min- utes. G GMT Toggle using Greenwich Mean Time for the END of this event. B Begin Toggle using GMT for the BEGINNING of this event. N Jump N Jump to even N. 1 Enable Toggle the Enabled/Disabled flag. 2 Insert Copy this event to make a new event. Adds to your total number of events. 3 Delete Delete this event. X EXecute Execute immediately. Marks this event as one that Opus should execute as soon as it sees the flag. The flag will be cleared by Opus before the event is executed. The event can be any of the external, Sca- nAll, or HouseKeeping events in your SCHED.DAT file. This will even execute a disabled event. The event that OEVENT will operate on will be in inverse video. You can use either the cursor keys or the '+' and '-' keys to move up and down through the events. OEVENT also know about PgUp, PgDn and Home for quicker movement around the events. When you get to an event you wish to change you can choose the appro- priate commands. For example '1', '2' or '3' changes an event from En- abled to Disabled to Deleted, or if you wish to change the behavior of OPUS as far as handling mail in an event that is already set to handle mail just use the 'Z' command. 'E' will edit everything about an event except for its enabled status. OEVENT is all menu-driven. I could never remember all the things I wanted to change in one pass, and OPUS crams so much more information into SCHED.DAT that it just isn't feasible to alter events from the command line. One subtle advantage is that OEVENT does allow zero-length events. That can be extremely helpful for doing special things like changing out- bound message packets from Hold to Crash with OMMM.EXE. OPUS will allow them and will honor them, but the internal Event editor won't allow zero length events, at least as of XX9X. Please forward any comments/suggestions/bug-reports to: Doug Boone 119/5 August 10, 1987: (Oevent 4a) Added the ESC command to allow you to exit without saving any changes. ^C should also have the same effect. Oevent opens the SCHED.BBS file, it reads the SCHED.BBS file, and it closes the SCHED.BBS file before it does anything else. This should be failsafe because what you are doing in memory does not affect what is stored on the disk until you Q)uit. Also worked on the problem of Oevent getting upset with people who ac- cidently hit letters when entering time values by reading in each char- acter as it is typed and checking it. Moved the display of the time to where you'd expect it to be while its being typed in. One odd effect of this change is the way partial times are entered, for example if you enter, "1:1", Oevent will assume you are trying to enter 1:01, and not 1:10. Hitting a carriage return in answer to a question should not scroll the screen up any more. It is a valid response for the Start and End time commands, telling Oevent that you don't what to change that event after all. Most other commands will now just ignore invalid responses. August 22, 1987: (Oevent 4b) Fixed errors induced in Oevent4A dealing with End of events. August 29, 1987: (Oevent 4c) Added the 'N' command to jump to a certain event, flag handling for SCAN ALL event (Not installed in OPUS yet!), and fixed Behavior Menu. February 10, 1988: (Nevent 0) Changed over to the new Opus event schedule. Added the new Behavior capabilities. February 12, 1988: (Nevent 0a) Added No-Local flag to Matrix Mask and to Nevent. Local calls will not be made during a Behavior Event that has this flag on. March 12, 1990: (Oevent 6) First Opus 1.10 release version. March 31, 1990: (Oevent 7) Fixed bug where Oevent was reading '-' for its internal commands, so that when Opus sent it a command line, Oevent would interpret the '-m##' as the command to make a new event file. Now OEVENT uses '/' or '=' for its internal commands. April 10, 1990: (Oevent 7.10) Fixed bug in external events where I wasn't setting the Forced/Informal bits properly. Opus would skip over some external events because of this. June 20, 1990: (Oevent 8.00) Added the 'A' Request Limit function. Use this for Behavior events to limit the amount of time that other mailers can do file requests during a particular behavior event.